Remove dev prefix in config-remote-sync when resource is renamed#4919
Merged
ilyakuz-db merged 1 commit intomainfrom Apr 10, 2026
Merged
Remove dev prefix in config-remote-sync when resource is renamed#4919ilyakuz-db merged 1 commit intomainfrom
ilyakuz-db merged 1 commit intomainfrom
Conversation
denik
approved these changes
Apr 10, 2026
When syncing remote resource changes back to config YAML, strip the dev name prefix (e.g. "[dev user] ") from job, pipeline, and dashboard names so only the unprefixed name is written to the config. Co-authored-by: Isaac
8447095 to
bd49741
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Remove current dev-prefix when config-remote-sync applies resource name changes to avoid duplicating it in the config
Why
If we don't do that users always need to remove dev prefix manually even for simple renames like
[prefix] foo_1 => [prefix] foo_2. If they don't do it that leads to job names like this:[dev username] [dev username] my_jobTests
Update acceptance tests